It is essential to thoroughly assess all the identified in-flight and planned projects as per the agreed Responsibility
Matrix For In-Scope Projects and to assess what activities are required prior to finalizing take-on activities.
-
For projects that go live before handover:
-
Review the Progress Reports for In-Scope Projects for the consequences on service post implementation.
Compare with Service Impact Report assessment expectations (this may include extra Knowledge Exchange)
-
Agree with relevant stakeholders what the commercial impact is and what activities are required
-
Agree whether any Client or incumbent rework is appropriate
-
Agree service level waivers (if appropriate) during initial service level measurement period (e.g. baseline
periods)
-
Develop contract Change Control Note (CCN) if required. Sign off on project sub-list for projects that go
live before handover
-
Mobilizing resources as previously identified (and shared with the Staffing stream).
-
For projects that Capgemini are to complete:
-
Obtain internal sign-off for estimates to complete
-
Raise Category List For In-Scope Projects for completion of these projects and discuss and agree with
relevant stakeholders (including Capgemini Run)
-
Agree service level waivers (if appropriate) during initial service level measurement period (e.g. baseline
periods)
-
Produce draft Change Control Note to service scope with implementation of project (signed-up after
implementation and stabilization)
-
Mobilize resources as previously identified (and shared with the Staffing stream)
-
For projects that the Client, incumbent(s)or other service provider(s) should complete (post service
handover):
-
Convert the list of activities Capgemini should undertake post service handover into a Statement of Work
and get Capgemini Run and Client sign-off
-
Get appropriate sign-off to service level waivers for the period post implementation (Early Life Support)
-
Produce draft Change Control Note to service scope with implementation of project (signed-up after
implementation and stabilization)
-
Mobilize resources as previously identified (and shared with the Staffing stream).
If there are any projects that transition is dependent on or are dependent on transition that have not progressed to
plan, then the relevant actions, change controls and/or mitigation plans need to be agreed and implemented.
Documented sign-off is required for agreed actions for in scope projects through Service Commencement. Lessons learnt
repository must be updated, if required.
|